home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950929-19951130
/
000043_news@columbia.edu_Sat Oct 7 08:45:51 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA09443
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sat, 7 Oct 1995 18:25:41 -0400
Received: by apakabar.cc.columbia.edu id AA09634
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 7 Oct 1995 18:25:40 -0400
Path: news.columbia.edu!panix!news.eecs.umich.edu!newshost.marcam.com!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit 3.14 under Win95 problem
Message-Id: <1995Oct7.144551.63053@cc.usu.edu>
Date: 7 Oct 95 14:45:51 MDT
References: <1995Oct4.102543@earth.medcolpa.edu> <453dpf$cie@apakabar.cc.columbia.edu>
Organization: Utah State University
Lines: 24
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <453dpf$cie@apakabar.cc.columbia.edu>, fdc@watsun.cc.columbia.edu (Frank da Cruz) writes:
> In article <1995Oct4.102543@earth.medcolpa.edu>,
> <schoffstall@earth.medcolpa.edu> wrote:
>>I'm running Kermit 3.14 under Win95. It runs fine when you shut
>>down Win95 and run a DOS session, but it won't run in a DOS box as a
>>Win95 process, apparently because it can't detect the port. After it
>>executes MSCUSTOM.INI, I get the message:
>>
>>?Warning: unknown hardware for port. Using the Bios as BIOS1
>>Unimplemented speed
>>?Cannot use RTS/CTS on non-UART parts
-----------
I have a suggestion for those afflicted with the above message.
Open the Windows Control Panel, choose Ports, tell Windows the IRQ and
port address of your COMx ports, restart Windows. Brave souls may wish
to further configure Windows to cope with 16550A UARTs, according to
whatever MS Windows instructions you happen to have.
I ran quick tests of MSK under WFW 3.11 here, and using serial
ports was clean every time. I had done the above.
The thought it Windows doesn't look at the hardware until forced,
and then on the first try it gets matters messed up. Thus repeated tries
with MSK to finally yield success is another way of telling Windows to do
the job properly. Configuring Windows should remove this forcing step.
Joe D.